IT personnel and organizational structure: for example, information system (IS) managers, support staff, network manager, database administrator
Development personnel: for example, manager, programmer, analyst, project manager
The system development life cycle (SDLC)
• Analysis of current situation
• Organizational requirements
• Methods of data collection: questionnaires, interviews, observation, literature searches
• Feasibility study
• Identification of possible IT solutions
• Requirements specification
• Justification of preferred IT solution
• Project plan (who, why, what, when and how part of the project)
• Project goals, scope and constraints, such as financial, time, technical, human-resource-related, risks, communication, procurement, quality
• Project initiation document
• Design considerations
• Inputs, data structure, processes, outputs, user interface
• Prototyping
• Development of the IT solution
• Initial testing, alpha testing
• Quality assurance and quality control
• Implementation
• Training and support of staff, documentation to support the new IT system
• Changeover methods: direct, phased and parallel running
• Beta testing
• Maintenance
• Phase out
Project management issues
• Need for project management
• Development methodologies: agile development and waterfall development
• Project management methodologies: for example, PRINCE2 (projects in controlled environments 2), SSADM (structured systems analysis and design method), PMBoK (project management body of knowledge), CMMI (capability maturity model integration)
• Iteration
• Time constraints, tasks, resources and milestones; Gantt and Pert charts
• Modelling systems: for example, entities, entity relationship diagrams (ERD), data flow diagrams
• Maintenance of legacy systems
• System support: for example, internal support, maintenance contract
• Incident management and escalation
The system development life cycle (SDLC)
• Analysis of current situation
• Organizational requirements
• Methods of data collection: questionnaires, interviews, observation, literature searches
• Feasibility study
• Identification of possible IT solutions
• Requirements specification
• Justification of preferred IT solution
• Project plan (who, why, what, when and how part of the project)
• Project goals, scope and constraints, such as financial, time, technical, human-resource-related, risks, communication, procurement, quality
• Project initiation document
• Design considerations
• Inputs, data structure, processes, outputs, user interface
• Prototyping
• Development of the IT solution
• Initial testing, alpha testing
• Quality assurance and quality control
• Implementation
• Training and support of staff, documentation to support the new IT system
• Changeover methods: direct, phased and parallel running
• Beta testing
• Maintenance
• Phase out
Project management issues
• Need for project management
• Development methodologies: agile development and waterfall development
• Project management methodologies: for example, PRINCE2 (projects in controlled environments 2), SSADM (structured systems analysis and design method), PMBoK (project management body of knowledge), CMMI (capability maturity model integration)
• Iteration
• Time constraints, tasks, resources and milestones; Gantt and Pert charts
• Modelling systems: for example, entities, entity relationship diagrams (ERD), data flow diagrams
• Maintenance of legacy systems
• System support: for example, internal support, maintenance contract
• Incident management and escalation